Build on an AI platform you own

Yes — and we like to be precise about it. The application layer (iblai/os), the skills-intelligence app (iblai/lms), the developer toolkit, SDK, platform skills and MCP server (iblai/vibe), the infrastructure CLI (iblai/infra-cli), and the documentation itself (iblai/docs) are all public on GitHub.

Read them, fork them, and run them yourself — this page links each repository directly, and every documentation page under /developer is generated from the repository it documents.

There is one core platform component that isn't public open source. You can use it as a fully managed, hosted service, or take it under a perpetual source-code license and self-host the entire stack.

Either way the principle is the same: you own all the code and the data, and your deployment is yours — nothing is locked away from you.

Want to see exactly where every line is drawn? Talk to us and we'll walk you through the whole architecture.

Install the skills with `npx skills add iblai/vibe --all` and type `/iblai-vibe-start` in Claude Code, Cursor or Codex: it asks what you are building, connects your organization, and scaffolds a production-ready Next.js app — SSO auth, agent chat, profiles, notifications and analytics wired to the platform.

Then add features one skill at a time from the catalog at /developer/skills, and deploy agents from the claws template library.

`/iblai-vibe-start` for a new app, `/iblai-api-login` for a script or CI job that never signs a user in, and `/iblai-vibe-ops-init` to copy the starter.

After that, pick by the data your app touches: the six core families — custom data per user, the user's profile, memory, custom data per organization, agent configuration, and analytics — each have a skill with a screen (`iblai-vibe-*`) and a headless twin (`iblai-api-*`). The catalog at /developer/skills is searchable by what you are trying to do.

ibl.ai exposes a full REST API for the platform — agents, chat, users, analytics, documents, credentials, and more.

The interactive API reference lives at /developer/api-reference, the OpenAPI schema is served at /api/docs-schema, and the production API base is platform.iblai.app.

The iblai/vibe repository ships agent skills plus a Model Context Protocol (MCP) server, so an AI agent can operate the entire ibl.ai platform through its REST API.

Install them with `npx skills add iblai/vibe --all` and your coding agent can create agents, manage users, and run workflows directly.

Yes. iblai/infra-cli is an interactive CLI that provisions the platform on your own AWS or GCP account with Terraform and configures servers with Ansible — and it can bootstrap any existing server.

You own all the code and the data, and the infrastructure too: cloud, VPC, on-premise, or fully air-gapped.

ibl.ai is model-agnostic. Run any LLM — Claude, GPT, Gemini, Llama, Mistral, Qwen, or your own fine-tune — and switch per workload without rebuilding your application.

You are never locked to a single vendor's models.

Every page under /developer/{repo} and /developer/guides is generated directly from the upstream GitHub repository by a sync script — the README and each file in the repo's docs directory.

That means there is no second copy to keep in sync: the engineers who ship the code write the documentation in the repo, and this site is the view. Pages that document the hosted platform backend, which has no public repository to mirror, live under /developer/platform and are maintained by hand.

Instead of per-seat SaaS, ibl.ai is usage-based or a flat perpetual license. What you build is a durable asset you own outright — not credits that evaporate when a subscription lapses.

ibl.ai serves 1.6M+ users from 400+ organizations and is family-owned and operated from New York, NY.